-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for podman v2 to podman-env command #9535
Conversation
Podman v1 (like 1.9.3) uses the varlink bridge, while podman v2 (like 2.1.x) uses a REST API. Both are using ssh for their transport, but the environment variables exported are different.
Travis tests have failedHey @afbjorklund, 1st Buildmake test
TravisBuddy Request Identifier: 75c013a0-1519-11eb-aff7-dd8cbeb067cc |
Dear @TravisBuddy it is just a Travis flake |
Codecov Report
@@ Coverage Diff @@
## master #9535 +/- ##
==========================================
+ Coverage 29.11% 29.21% +0.09%
==========================================
Files 172 172
Lines 10461 10556 +95
==========================================
+ Hits 3046 3084 +38
- Misses 6990 7047 +57
Partials 425 425
|
a341305
to
bfefa72
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund, medyagh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Podman v1 (like 1.9.3) uses the varlink bridge,
while podman v2 (like 2.1.x) uses a REST API.
Both are using ssh for their transport, but the
environment variables exported are different.
Not using
sudo
anymore, so user needs root access.See #8596 for how to set that up for the "docker" user
Tested OK with 1.9.3 and 2.1.1 minikube profiles.
But don't recommend using podman 2.0.x (at all)